Drop ppc64le architecture from Docker build scripts #378
Conversation
We don't build images for ppc64le anyways, so it's very unlikely that this functionality is being used. Signed-off-by: Mikhail Krinkin <[email protected]>
|
we're working on getting it working still. missed this last week. envoyproxy/envoy#25090 (comment) however, we're not using this afaik , just |
|
FYI @Jenkins-J |
|
@clnperez flagging that when we shift to using the bazel llvm toolchain we will still be using the same source for llvm bins - ie: https://github.com/llvm/llvm-project/releases/ in the event that the current envoy llvm version is not available for ppc64le - you will either need to patch to set an llvm version that is available - or have (someone at the) llvm project add it - creating the bins is a "volunteer" thing |
|
@phlax I talked with our toolchain team, and it sounds like their agreement with that llvm volunteer team is that we own our own binares. Power hardware isn't so easy to come by. :D (but i'll not miss an opportunity to remind folks in opensource projects they request Power VMs at OSU: https://osuosl.org/services/powerdev) They're here: https://github.com/IBM/llvm-project |
We don't build images for ppc64le anyways, so it's very unlikely that this functionality is being used.
Tested that the change does not break anything by running:
Fixes #377
+cc @phlax @clnperez